To ensure the language toggle follows the design guidelines here:

https://design.tax.service.gov.uk/hmrc-design-patterns/welsh-language-toggle/

This what the final output looks like:

Final HTML for when English is selected.

<nav class="language-toggle hmrc-language-select" aria-label="Language switcher">
    <ul class="hmrc-language-select__list language-toggle" style="display: block;">
    
        
            <li class="hmrc-language-select__list-item" style="display: inline-block;">
                <span aria-current="true">English</span>
            </li>
        
        
             | 
        
    
        
            <li class="hmrc-language-select__list-item" style="display: inline-block;">
                <a id="cymraeg-switch" href="/customs/register-for-cds/language/cymraeg" hreflang="cy" lang="cy" rel="alternate" target="_self" data-sso="false" data-journey-click="customs-rosm-frontend:language: cy">
                    <span class="visually-hidden">Newid yr iaith ir Gymraeg</span>
                    <span aria-hidden="true">Cymraeg</span>
                </a>
            </li>
        
        
    
    </ul>
</nav>

And for welsh:

<nav class="language-toggle hmrc-language-select" aria-label="Switcher iaith">
    <ul class="hmrc-language-select__list language-toggle" style="display: block;">
    
        
            <li class="hmrc-language-select__list-item" style="display: inline-block;">
                <a id="english-switch" href="/customs/register-for-cds/language/english" hreflang="en" lang="en" rel="alternate" target="_self" data-sso="false" data-journey-click="customs-rosm-frontend:language: en">
                    <span class="visually-hidden">Change language to English</span>
                    <span aria-hidden="true">English</span>
                </a>
            </li>
        
        
             | 
        
    
        
            <li class="hmrc-language-select__list-item" style="display: inline-block;">
                <span aria-current="true">Cymraeg</span>
            </li>
        
        
    
    </ul>
</nav>

Hi @rashadmughal I've taken a bit of a look at this. I'm quite new to the Plat UI team so apologies if my reviews aren't as quick as Jo's might have been here. I need to do a bit more investigation to understand the context of play-ui and where it pulls it's styles from before I can finish reviewing but there are a few small changes I can see would be good to make (just a couple of attributes on links, nothing big) that I'll add as comments while I get myself up to speed properly (just explaining so you're aware there there might be extra feedback after these initial comments)

@rashadmughal I've discussed this a bit more with other devs from Plat UI team and it looks like the classes you're using here depend on styles from hmrc/hmrc-frontend where as play-ui components can only rely on styles from hmrc/assets-frontend - so to create this component in play-ui it would need to be structured like the language toggle from assets-frontend https://github.com/hmrc/assets-frontend/blob/2692f3349017691e263a64142bde58d84ead4e2e/assets/components/language-selector/language-selector.html

Though we'd strongly recommend that your most future proof option here is to migrate away from play-ui where possible and use hmrc/play-frontend-hmrc which already integrates a language select component https://github.com/hmrc/play-frontend-hmrc/blob/master/src/main/twirl/uk/gov/hmrc/hmrcfrontend/views/components/hmrcLanguageSelect.scala.html

Though we totally understand migration is almost always simpler said than done! So Plat UI is able to help with questions and advice when migrating

Hi @rashadmughal just to add to this, if you do update this PR to use assets-frontend classes to style the component from the example I linked then the other attributes (aria-label, aria-current, lang attributes, and visually hidden copy) shouldn't be removed - the example from assets-frontend doesn't have those bits (but you've got them here) and they are needed for this to meet our current accessibility standards - they're just missing from assets-frontend example because it's not been updated in quite a long time it seems!